SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
PHP

PHP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your PHP code

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Allowing unfiltered HTML content in WordPress is security-sensitive

           Security Hotspot
        4. Allowing unauthenticated database repair in WordPress is security-sensitive

           Security Hotspot
        5. Allowing all external requests from a WordPress server is security-sensitive

           Security Hotspot
        6. Disabling automatic updates is security-sensitive

           Security Hotspot
        7. WordPress theme and plugin editors are security-sensitive

           Security Hotspot
        8. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Manual generation of session ID is security-sensitive

           Security Hotspot
        11. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        12. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        13. Controlling permissions is security-sensitive

           Security Hotspot
        14. Reading the Standard Input is security-sensitive

           Security Hotspot
        15. Signaling processes is security-sensitive

           Security Hotspot
        16. Using command line arguments is security-sensitive

           Security Hotspot
        17. Using Sockets is security-sensitive

           Security Hotspot
        18. Configuring loggers is security-sensitive

           Security Hotspot
        19. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        20. Encrypting data is security-sensitive

           Security Hotspot
        21. Using regular expressions is security-sensitive

           Security Hotspot
        22. Deserializing objects from an untrusted source is security-sensitive

           Security Hotspot
        23. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        24. Disabling CSRF protections is security-sensitive

           Security Hotspot
        25. Creating cookies with broadly defined "domain" flags is security-sensitive

           Security Hotspot
        26. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        27. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        28. Writing cookies is security-sensitive

           Security Hotspot
        29. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        30. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        31. Formatting SQL queries is security-sensitive

           Security Hotspot
        32. Hard-coded credentials are security-sensitive

           Security Hotspot
        33. Dynamically executing code is security-sensitive

           Security Hotspot
        34. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        Having a permissive Cross-Origin Resource Sharing policy is security-sensitive. It has led in the past to the following vulnerabilities:

        • CVE-2018-0269
        • CVE-2017-14460

        Same origin policy in browsers prevents, by default and for security-reasons, a javascript frontend to perform a cross-origin HTTP request to a resource that has a different origin (domain, protocol, or port) from its own. The requested target can append additional HTTP headers in response, called CORS, that act like directives for the browser and change the access control policy / relax the same origin policy.

        Ask Yourself Whether

        • You don’t trust the origin specified, example: Access-Control-Allow-Origin: untrustedwebsite.com.
        • Access control policy is entirely disabled: Access-Control-Allow-Origin: *
        • Your access control policy is dynamically defined by a user-controlled input like origin header.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • The Access-Control-Allow-Origin header should be set only for a trusted origin and for specific resources.
        • Allow only selected, trusted domains in the Access-Control-Allow-Origin header. Prefer whitelisting domains over blacklisting or allowing any domain (do not use * wildcard nor blindly return the Origin header content without any checks).

        Sensitive Code Example

        PHP built-in header function:

        header("Access-Control-Allow-Origin: *"); // Sensitive
        

        Laravel:

        response()->header('Access-Control-Allow-Origin', "*"); // Sensitive
        

        Symfony:

        use Symfony\Component\HttpFoundation\Response;
        
        $response = new Response(
            'Content',
            Response::HTTP_OK,
            ['Access-Control-Allow-Origin' => '*'] // Sensitive
        );
        $response->headers->set('Access-Control-Allow-Origin', '*'); // Sensitive
        

        User-controlled origin:

        use Symfony\Component\HttpFoundation\Response;
        use Symfony\Component\HttpFoundation\Request;
        
        $origin = $request->headers->get('Origin');
        
        $response->headers->set('Access-Control-Allow-Origin', $origin); // Sensitive
        

        Compliant Solution

        PHP built-in header function:

        header("Access-Control-Allow-Origin: $trusteddomain");
        

        Laravel:

        response()->header('Access-Control-Allow-Origin', $trusteddomain);
        

        Symfony:

        use Symfony\Component\HttpFoundation\Response;
        
        $response = new Response(
            'Content',
            Response::HTTP_OK,
            ['Access-Control-Allow-Origin' => $trusteddomain]
        );
        
        $response->headers->set('Access-Control-Allow-Origin', $trusteddomain);
        

        User-controlled origin validated with an allow-list:

        use Symfony\Component\HttpFoundation\Response;
        use Symfony\Component\HttpFoundation\Request;
        
        $origin = $request->headers->get('Origin');
        
        if (in_array($origin, $trustedOrigins)) {
            $response->headers->set('Access-Control-Allow-Origin', $origin);
        }
        

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2021 Category A7 - Identification and Authentication Failures
        • developer.mozilla.org - CORS
        • developer.mozilla.org - Same origin policy
        • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
        • OWASP HTML5 Security Cheat Sheet - Cross Origin Resource Sharing
        • CWE - CWE-346 - Origin Validation Error
        • CWE - CWE-942 - Overly Permissive Cross-domain Whitelist
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use